Migrating data for web content management systems

ABSTRACT

A computer-based system and related method are provided for migrating data associated with a website from a first Web content management (WCM) platform to a second WCM platform. The data migrated can include templates, user and group data files, content files (media, texts and others), workflows, authorizations, among others. The system and related method can further include a transformation capability that enables modifications to website data elements during migration, including but not limited to templates, HTML, users, metadata, file assets, and content such as images, links, and text during migration. In this manner, web administrators can modify the website design during migration to a new WCM platform within an integrated process.

CROSS REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional App. No.61/863,886, filed Aug. 8, 2013, which is incorporated by reference.

FIELD OF THE INVENTION

The present invention relates generally to data migration systems and,more particularly, a system and related method for migrating databetween web content management systems.

BACKGROUND OF THE INVENTION

Web content management (WCM) systems are used to create, manage, andcontrol collections of web-based material, e.g., Hypertext MarkupLanguage (HTML) documents, PHP documents, images, and others. A WCMsystem generally facilitates document control, editing, timelinemanagement, and publication of a website. For instance, a typical WCMsystem can provide one or more of the following features: automatedtemplates, easily editable content, workflow management, documentmanagement, and content virtualization, among others. Using a WCM systemprovides developers with tools that allow for the creation of attractiveand well-designed web pages and/or websites with uniform or relatedlayouts.

Modern websites often use web content management (WCM) systems. WCMsystems allow website administrators to control the content of their webpages, among other features. For instance, WCM systems allow users toadd or edit information on a web page without requiring programmingknowledge and to manage content workflows and user permissions.

With the growing complexity of website design, content management hasevolved from merely managing the storage and access of document data onlocal computers to controlling increasingly complex data such as HTMLcodes, modules, permissions, and the linking of sub-pages and hostedimages to a web site, with near real-time updates.

Many web content management (WCM) systems exist in the marketplace, suchas Sitecore® (of Sitecore Corporation), Drupal™ (open source), Adobe CQ®(of Adobe Systems Incorporated), HP Autonomy TeamSite™ (of HP Autonomy),Oracle Fatwire (of Oracle Corporation), Microsoft SharePoint (ofMicrosoft Corporation), EPiServer® (of EPiServer Inc.), OpenText® website management (of OpenText Corp.), Ektron® WCM (of Ektron, Inc.),among others. Each of the systems has unique features andfunctionalities. As general matter, each of these systems has aninternal working environment that enables web administrators to controland manipulate website content prior to publishing the site on the web.Moreover, within its internal working environment, each WCM system hasunique terminology and linking methodologies. This enables these systemsto provide ease of use for within their respective environments, butmake transportability of websites between systems problematic.

The state of the art in website design and WCM systems advances quickly.As such, site administrators periodically elect to move their websitesto new WCM systems to keep pace with the rapidly increasingsophistication of web-based systems. In addition, as a company grows,its requirements for a WCM system change. With a small company, a basicWCM system might be satisfactory. However, as companies grow, theyfrequently have the need to use increasingly complex WCM systems. Thus,companies will find the need to migrate between WCM systems.

However, migration can be a difficult problem. Current approaches formigrating content can be labor-intensive and highly vulnerable to error.As a result, some companies are forced to write individualized code toautomate part of the data migration process, but this is highlytechnical and time-consuming. As a result, most data migration projectseither fail or go over budget.

Off-the-shelf systems for data migration exist and can be generallyeffective from transferring data files, however, shortfalls exist. Forexample, such systems typically migrate the published website files. Asa result, the functionality that existed within the internal workingenvironment of the first WCM system is lost, such as internal linking,templates, WCM-specific terminology, and other features, which the webadministrator often must manually correct within the new WCMenvironment. Moreover, current approaches can be slow—it can takeseveral days to transfer between WCM systems, resulting in times whenthe website is unavailable.

It should, therefore, be appreciated that there exists a need for a datamigration system that rapidly transfers all the data needed.

SUMMARY OF THE INVENTION

It is an object of the present invention to provide a system that movesdata, including page templates, modules, and other content, across WCMsystems and re-links pages, modules, and images, making the new siteoperate like the old site automatically.

Briefly, and in general terms, the invention provides a system andrelated method for migrating data associated with a website from a firstWeb content management (WCM) platform to a second WCM platform. The datamigrated can include templates, user and group data files, content files(media, texts and others), workflows, authorizations, among others. Thesystem and related method can further include a transformationcapability that enables modifications to website data elements duringmigration, including but not limited to templates, HTML, users,metadata, file assets, and content such as images, links, and textduring migration. In this manner, web administrators can modify thewebsite design during migration to a new WCM platform within anintegrated process.

In a detailed aspect of an exemplary embodiment, the system provides anextensible application-programming interface (API) that allowsprogramming support for new web sources or target platforms. The usercan create custom transformations that modify elements of the migratedfiles as they are moved between the WCM systems. Back-end runningprocesses and UI enable the user to set up the transformation processthen periodically check the progress. The system architecture re-linkspages, modules, and images so that the transformed site in the new WCMenvironment connects items in a similar manner as the old WCMenvironment.

In another detailed aspect of an exemplary embodiment, the systemincludes a library of WCM connectors. The connectors integrate WCMsystems, using executable code to translate data from the format of theWCM environment to and from a standardized form used by the migrationengine.

For purposes of summarizing the invention and the advantages achievedover the prior art, certain advantages of the invention have beendescribed herein. Of course, it is to be understood that not necessarilyall such advantages may be achieved in accordance with any particularembodiment of the invention. Thus, for example, those skilled in the artwill recognize that the invention may be embodied or carried out in amanner that achieves or optimizes one advantage or group of advantagesas taught herein without necessarily achieving other advantages as maybe taught or suggested herein.

All of these embodiments are intended to be within the scope of theinvention herein disclosed. These and other embodiments of the presentinvention will become readily apparent to those skilled in the art fromthe following detailed description of the preferred embodiments havingreference to the attached figures, the invention not being limited toany particular preferred embodiment disclosed.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention will now be described, by way ofexample only, with reference to the following drawings in which:

FIG. 1A is a simplified block diagram of a system for migrating data forWCM systems in accordance with the present invention.

FIG. 1B is a screenshot of a portion of executable code of a connectorfor the system of FIG. 1

FIG. 2 is a simplified flow chart for the system of FIG. 1, depictingrepresentative steps for initiating a migration from a first WCM systemto a second WCM system.

FIG. 3 is a simplified flow chart for the system of FIG. 1, depictingrepresentative steps for migration order of website data.

FIGS. 4-6 are exemplary dashboard interfaces for the system of FIG. 1,depicting an interface for connecting with the source WCM and the targetWCM systems

FIG. 7 is an exemplary dashboard interface for the system of FIG. 1,depicting an interface for selecting templates from the source WCMsystem for migration to the target WCM system.

FIG. 8 is an exemplary dashboard interface for the system of FIG. 1,depicting an event console that displays the status of the migrationwhile the processes is running.

FIG. 9 is an exemplary dashboard interface for the system of FIG. 1,depicting an interface for determining content structure within thesource WCM system.

FIG. 10 is an exemplary dashboard interface for the system of FIG. 1,depicting an interface for content migration.

FIG. 11 is an exemplary dashboard interface for the system of FIG. 1,depicting an interface locating a template within an origin WCM system.

FIG. 12 is an exemplary dashboard interface for the system of FIG. 1,depicting an interface for viewing templates within the target WCMsystem.

FIG. 13 is an exemplary dashboard interface for the system of FIG. 1,depicting an interface for configuring template mapping.

FIG. 14 is an exemplary dashboard interface for the system of FIG. 1,depicting an interface for template mapping.

FIG. 15 is an exemplary dashboard interface for the system of FIG. 1,depicting an interface for configuring fields within the templatemapping architecture.

FIG. 16 is an exemplary dashboard interface for the system of FIG. 1,depicting an interface for reviewing migrated content within the targetWCM system.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Embodiments described herein are directed to a computer-based system andmethod for efficiently migrating any or all data associated with awebsite from a first WCM platform to a second WCM platform. The datamigrated can include templates, user and group data files, content files(media, texts and others), workflows, authorizations, among others.

The system further includes a transformation capability that enablesmodifications to website data elements during migration. The websiteadministrator can transform CMS constructs including but not limited totemplates, HTML, users, metadata, file assets, and content such asimages, links, and text during migration. In this manner, webadministrators can modify the website design during migration to a newWCM platform within an integrated process. In the exemplary embodiment,the system resides in a centralized server and accesses multiple serversin the local network or in the cloud.

With reference now to FIG. 1A-B, the system 1 includes a migrationengine 6 and a library of WCM connectors, e.g., 4(a, b), that provideAPI-level integration with WCM systems. The connectors compriseexecutable code that translates data formatted to comply with theinternal working environment of the particular WCM system to astandardized format used by the migration engine 6 (see, e.g., FIG. 1B).

The system 1 is able to migrate not only content items, but also otherdata items typically critical to a complete WCM including, for example,the following:

Templates of the selected project or website;

Pages—Content on website pages;

Linkages—Navigation from page to page;

Page Components—Scripts controlling interaction with the server;

Media—Images, videos, charts, and so on;

Users—Users of the selected server;

Groups—User groups of the selected server;

Templates of the selected project;

Metadata of the selected project;

Workflows of the selected project; and

Authorization Packages of the selected project.

The system 1 connects the source WCM system to the templates to provideform, style, and content standardization for the publication andpresentation webpages of a website. For example, in an e-commerce site,a template for the display of products can ensure the each product isdisplayed in consistent matter with the appropriate images and text.

The system 1 further includes a template mapper 7 to allow the user toeasily map the content from the original WCM A to the target WCM B. Thisfeature is primarily used to seamlessly move content from the originalWCM to the target WCM by automatically reconfiguring to the appropriateformat. It may also be used to incorporate new design features into thenew website.

The system further includes the ability to apply customizetransformations 8 (a-n) to data during the migration process. In thismanner, the user can modify the website as it is migrated from thesource of WCM system to the target of WCM system. In the exemplaryembodiment, the system executes the transformations in serial order(see, e.g., FIGS. 2 and 3).

The system 1 enables users to migrate all or portions of website contentbetween WCM systems. The following presents a few examples of variousmigrations that can be performed with the system.

Example 1—Template Migration

The system 1 migrate templates from one WCM to another. For example, thesystem can migrate templates from the Origin WCM system (e.g. OpenText)to the target WCM (e.g. Sitecore). The process can begin with a blanktarget WCM project. The target WCM content editor interface is empty,which is the default for the target WCM. The site that will be migratedto the target WCM can be viewed in the Origin WCM system.

With reference now to FIGS. 4-8, the source and target WCM systems (20,22, respectively) are set via the system dashboard 24 for the system tomigrate. From the dashboard (24) to set the correct source and targetWCM. The dashboard enables the user to select the WCM provider and loginto the WCM's server 26 to select the desired project list 30 formigration. The same process is performed for connecting to the targetWCM 22, (select the target WCM as the provider and select the server).

The system populates a list of all the available templates from thissource WCM system. The user selects the templates for migration. In theexemplary embodiment, the template icon is located in the leftnavigation 32. The user can migrate all templates by choosing “selectall” option 34 (FIG. 7). The user can initiate the migration byselecting the play icon 42 to run the migration.

With reference now to FIG. 8, the system provides an event console 44that shows the status of the migration while the migration is running.The event console enables the user to view the progress of the migrationwithout having to be actively involved in the process. The event console44 has four clickable tabs that allow the user to see different types ofinformation: “Job Status”, “All Events” 46, “Completed Events” 50, and“Errors” 52. By selecting the “All Events” tab 46, the system willdisplay shows all the events in the migration as they occur. The“Details” bar 48 can be used to show more or less information about theevents being migrated. The “Completed Events” tab 50 will list theevents completed when the migration is complete. The “Errors” tab 52will list any errors during the migration. The user has the option toclose the event console at any time. When the transfer is complete,“Completed” is displayed in green.

The system allows the user to check the migrated templates in the targetWCM after migration is complete. The user can check the target WCMproject and open the templates, layouts and sub-layouts notes 54 tocheck that all the templates have been migrated. The system allows youto compare an original template in the Origin WCM system to a newlymigrated template in the target WCM. Open the HTML template in theOrigin WCM system and the target WCM at the same time to compare them toeach other.

Since WCM systems typically use different terminology, the system comeswith transformers to ensure that items that are described differentlyfrom one WCM to another are migrated correctly. Overall, the system canbe used to migrate all templates from one WCM to another.

Example 2—All Content Migration

With reference now to FIGS. 9-10, the system enables the user to migrateall your content from the Origin WCM system (e.g. OpenText) to thetarget WCM (e.g. Sitecore). From the Origin WCM system, click onSmartTree 56 to see how the content is structured, by selecting on the“SmartEdit” tab 58 (FIG. 9). The target WCM must also have alreadyacquired the media library prior to content migration. The images 60 canbe installed using the target WCM installation wizard.

With reference now to FIG. 10, the system enables the user to selectcontent for migration via an intuitive interface. A content tree 74 forthe origin WCM system is depicted, so the user can select one or morenodes 76 to migrate. Then the user selects the type(s) of content tomigrate 78. In a full migration, all the boxes should be checked. Youcan also select the migration depth, indicating how deeply the systemwill migrate under the node selected, up to an unlimited depth.

The user can initiate migration by selecting the start arrow 84 to beginthe migration. As discussed above, an event console will expand to showall the migrations taking place, after the migration begins. The consolecan be used to view information about each event. The job status tab inthe event console will indicate when the migration is complete. Once amigration is completed, the user can review the migrated content.

Example 3—Content Migration and Site Redesign

With reference now to FIGS. 9-16, the system can be used to redesigntemplates for the website during content migration, by utilizing atemplate mapper.

The user can locate the template used for the homepage in the origin WCMsystem (FIG. 11) and navigate to find a template used for a single pagein the site. The system further enables the user to view the templateelements of a single page. Next, the use can further view the newtemplates in the target WCM (FIG. 12). The use can design the targettemplate to incorporate the new design features for the website to behosted by the target WCM system.

To begin the migration, the user creates a new configuration 90 andconfigures the source 92 and target 94 WCM (FIG. 13). As discussedabove, the user selects the content 96 to migrate from the source. Theuser also selects the type of content, the migration depth, selects thetarget location for the content, and clicks “Save”.

The user then utilizes the template mapper 98 to map the old template inthe origin WCM system 100 to the new template in the target WCM 102(FIG. 14). Using this feature, the user can identify how the contentshould be mapped within the template (FIG. 15). The user creates a newtemplate mapper by selecting a name, the content to include, the typesof content to include (e.g. pages, page links, etc.), and the targetlocation. Source and target WCM providers are selectable from drop boxlists. The template mapper can then map the source template to thetarget template. In an exemplary embodiment, the source WCM is in OpenText format and the destination WCM is on SitePort. Features such asheaders are declared using different code. The template mapper adaptsthe code to the new WCM template, enabling a seamless transition. Theuser can now run the migration to implement the changes by selecting atemplate mapper and clicking “Run.”

Using the event console, the user can check the target WCM to see thatthe content was migrated correctly (FIG. 16). The user can use theEditor tab 114 to edit content on the page directly and add links to thenewly migrated page. Finally, content is published to the new site 116and the user may check the results. Overall, the system's templatemapping feature allows the user to move a site from one WCM to anotherquickly and easily.

It should be appreciated from the foregoing that the present inventionprovides a computer-based system and method for efficiently migratingany or all data associated with a website from a first WCM platform to asecond WCM platform. The data migrated can include templates, user andgroup data files, content files (media, texts and others), workflows,authorizations, among others. The system further includes atransformation capability that enables modifications to website dataelements during migration. For example, the website administration cantransform one or more templates during migration. In this manner, webadministrators can modify the website design and is transferred to andnew WCM platform within an integrated process

Embodiments of the present invention may comprise or utilize specialpurpose or general-purpose computers including computer hardware, suchas, for example, one or more processors, servers, communication modules,and system memory, and the like. Embodiments within the scope of thepresent invention also include physical and other computer-readablemedia for carrying or storing computer-executable instructions and/ordata structures.

Embodiments of the present invention can exist in networked environment.The “network,” unless otherwise indicated, is defined as one or moredata links that enable the transport of electronic data between computersystems, modules or other electronic devices, via communicationsconnection (e.g., hard-wired, wireless, or a combination of hardwired orwireless).

Computer-executable instructions comprise, for example, instructions anddata, which cause a general-purpose computer, special purpose computer,or special purpose-processing device to perform a certain function orgroup of functions. The computer executable instructions may be, forexample, binaries, intermediate format instructions such as assemblylanguage, or even source code. Although the subject matter has beendescribed in language specific to structural features and/ormethodological acts, it is to be understood that the present inventionis not necessarily limited to the described features or acts.

Moreover, those skilled in the art will appreciate that the inventionmay be practiced in network computing environments with many types ofcomputer system configurations, including, personal computers, desktopcomputers, laptop computers, message processors, hand-held devices,multi-processor systems, microprocessor-based or programmable consumerelectronics, network PCs, minicomputers, mainframe computers, mobiletelephones, PDAs, pagers, routers, switches, and the like. The inventionmay also be practiced in distributed system environments where local andremote computer systems, which are linked (either by hardwired datalinks, wireless data links, or by a combination of hardwired andwireless data links) through a network, both perform tasks. In adistributed system environment, program modules may be located in bothlocal and remote memory storage devices.

The present invention provides a computer-based system and relatedmethod for migrating data associated with a website from a first Webcontent management (WCM) platform to a second WCM platform. The datamigrated can include templates, user and group data files, content files(media, texts and others), workflows, authorizations, among others. Thesystem and related method can further include a transformationcapability that enables modifications to website data elements duringmigration, including but not limited to templates, HTML, users,metadata, file assets, and content such as images, links, and textduring migration. In this manner, web administrators can modify thewebsite design during migration to a new WCM platform within anintegrated process.

The present invention has been described above in terms of presentlypreferred embodiments so that an understanding of the present inventioncan be conveyed. However, there are other embodiments not specificallydescribed herein for which the present invention is applicable.Therefore, the present invention should not to be seen as limited to theforms shown, which is to be considered illustrative rather thanrestrictive.

What is claimed is:
 1. A computer-implemented system including ahardware processor and a memory for migrating data for web contentmanagement (WCM) systems from a first WCM platform to a second WCMplatform, comprising: a first connector module in digital communicationwith a first WCM platform to retrieve data from the first WCM platform,the first connector module translates the retrieved data from a formatfor the first WCM platform to a standardized format for the system,resulting in pre-migrated standardized data; a migration engine indigital communication with the first connector module, in which themigration engine receives the pre-migrated standardized data from thefirst connector module and transforms said pre-migrated standardizeddata to post-migrated standardized data, in which said post-migratedstandardized data include migrated templates from a first WCM platformto a second WCM platform; a template mapper in digital communicationwith the first connector module and the migration engine, in which thetemplate mapper identifies a plurality of origin templates of the firstWCM platform and creates a mapped relationship between the plurality oforigin templates and a plurality of target templates of the second WCMplatform, and said mapped relationship is communicated to the migrationengine to facilitate migration of the origin templates to the targettemplates, resulting in said post-migrated standardized data; and asecond connector module in digital communication with the migrationengine and with the second WCM platform, wherein the second connectormodule translates the post-migrated standardized data to a format forthe second WCM platform.
 2. The system as defined in claim 1, whereinthe retrieved data includes webpage templates, website linkages amongwebpages, website scripts, digital media files, and user and group data.3. The system as defined in claim 1, wherein the first connector modulecomprises executable code that translates the retrieved data to thepre-migrated standardized data.
 4. The system as defined in claim 1,further comprising a transformer that enables modifications to websitedata elements during migration, including but not limited to templates,HTML, users, metadata, file assets, and content such as images, links,and text.
 5. The system as defined in claim 1, wherein the migrationengine generates post-migrated standardized data that includes targettemplates, webpages, and media file, that are operably linked.
 6. Thesystem as defined in claim 1, wherein the template mapper populates aselectable list presented on a user display screen, the list comprisesall templates of the first WCM platform.
 7. A computer-implementedmethod for migrating data for web content management (WCM) systems froma first WCM platform to a second WCM platform, comprising: retrievingdata from a first WCM platform via a first connector module in digitalcommunication with the first WCM platform; translating the retrieveddata from a format for the first WCM platform to a standardized formatfor a migration engine that is in digital communication with the firstconnector module, resulting in pre-migrated standardized data, via thefirst connector module; mapping relationships between origin templatesof the first WCM platform and target templates for the second WCMplatform, via a template mapper that is in digital communication withthe migration engine, and said mapped relationships between the origintemplates and the target templates are communicated to the migrationengine; transforming the pre-migrated standardized data received fromthe first connector module using the mapped relationships received fromthe template mapper to a post-migrated standardized data, via themigration engine; retrieving the post-migrated standardized data via asecond connector module in digital communication with the migrationengine; translating the post-migrated standardized data to resultantdata in a format for the second WCM platform, via the second connectormodule; and transmitting the resultant data to the second WCM platform.8. The method as defined in claim 7, wherein the retrieved data includeswebpage templates, website linkages among webpages, website scripts,digital media files, and user and group data.
 9. The method as definedin claim 7, wherein the first connector module comprises executable codethat translates the retrieved data to the pre-migrated standardizeddata.
 10. The method as defined in claim 7, further comprising atransformer that enables modifications to website data elements duringmigration, including but not limited to templates, HTML, users,metadata, file assets, and content such as images, links, and text. 11.The method as defined in claim 7, wherein the migration engine generatespost-migrated standardized data that includes target templates,webpages, and media file, that are operably linked.
 12. The method asdefined in claim 7, wherein the template mapper populates a selectablelist presented on a user display screen, the list comprises alltemplates of the first WCM platform.